Task dismissal introspection

Author: John | Created: 2016-07-28 8:44 | Last Activity: 2016-08-5 22:30

Original Post

2016-07-28 8:44
I've had an idea for a while that might be of interest. It's just a simple rule about task dismissal: dismissed tasks need to change in order to get back on a list.

In GTD terms, if a task isn't being done, the Next Action is probably wrong:

- I shouldn't do it (no resubmission necessary)
- It's no longer the right approach (task becomes the better approach)
- Task can't be done at this time (task becomes 'add to calendar')
- Task depends on prior action (task becomes the real next action)
- I don't want to do it (task becomes 'just get folder out' or is dismissed)

You get the idea. I like the mild enforced introspection.

Sorry if this has already been mentioned.

Reply by Cricket

2016-08-5 22:30
Next Action was a big step forward for me. Fortunately (for me), it's now a habit.

My colleagues find it annoying, mostly because it forces the introspection you describe. It's easy to agree to a project in principle, and even commit the group. Finding a volunteer to take the next action is the real test, and I insist we do that for a few next actions before letting the group commit to the project as a whole.